ABC Global Functionality Module — Testing Playbook

Create User: Navigate to System Admin → Users. Click "New User". Enter Last Name (required), First Name (required), Email (required, validated). System generates temporary password, sends password reset email to user. User logs in, sets permanent password (10 char min, 3 of 4 types: lower/upper/number/special). Status defaults to Active.

Clone User: Click "Clone" on existing user row. System copies user's permissions and defaults to new user. Staff updates name/email, confirms. Useful for onboarding replacements (staff departs, new hire clones their profile, inactivates old account).

Browse Users: Users list shows Last Name, First Name, Email, Status (Active/Inactive), Last Login, Created Date. Filter by Status or search by name. Click user row to view details.

Edit User: Click user row to open edit modal. Update Last Name, First Name, Email, Status. Confirm changes. If changing to Inactive, confirmation prompt: "Deactivate user? They will not be able to log in." If changing to Active, confirmation: "This will re-enable their login."

Delete User: Click "Delete" button (available only if user has zero record history—no transactions, events created, etc.). Confirmation required: "Permanently delete user? This cannot be undone." Once deleted, user is removed from system entirely.

Masquerade: Click "Login As" on user row (L3 Users and National only). Opens new tab with vivid banner: "[You are logged in as: FirstName LastName]". Staff can test user's permissions, debug issues, perform actions on user's behalf. All actions logged to audit trail with masquerader attribution. Click "Exit Masquerade" to return to own account.

Password Reset: Click "Reset Password" on user row. System sends password reset email immediately. User clicks link, sets new password. If user forgot password, they can self-serve via login screen "Forgot Password" link.

Permission Matrix: 15 modules (Events, Membership & Dues, Contacts, etc.) × 4 permission levels = 60 permission settings per user.

Permission Levels:

• L0 (Restricted) — No access. Module not visible in navigation.
• L1 (View) — View-only access. Can search, filter, view records. Cannot create, edit, or delete.
• L2 (Edit) — Create and edit own records. Can delete own records (if no history). Cannot access admin screens.
• L3 (Admin) — Full access. Create/edit/delete any record. Access admin screens, manage settings, export data, access masquerade.

Super User Flag: When enabled, automatically sets all 15 modules to L3 (Admin). Useful for National staff and system admins. Overrides individual module settings.

Assign Permissions: Click user row, scroll to "Permission Groups" section. For each of 15 modules, toggle permission level (L0/L1/L2/L3). If Super User flag is enabled, individual module settings are greyed out. Save changes. Navigation is updated immediately for next login.

Permission Enforcement: System checks permission on every action. Attempt to access restricted module shows 403 Forbidden. Attempt to edit without L2+ shows "Permission Denied" message. Buttons for create/edit/delete are hidden from L0/L1 users.

Browse Lookup Tables: Navigate to System Admin → Lookup Tables. Table shows all configurable code/label tables (Chapter, Department, Status, etc.). Filter by table name or search. Click table to manage codes.

Edit Lookup Table (Unlocked): If table is unlocked, staff can edit codes directly. Edit-in-place: click code row, change label or add new code, hit Enter. System saves immediately. Column indicator shows "Unlocked" in green. All changes logged to audit trail.

Locked Table (National Lock): If National has locked entire table, chapter sees "Locked by National" banner. No edits allowed. Staff must contact National via Zoho email workflow to request unlock or modification.

System Lock (Individual Code): Critical codes (e.g., "Chapter Default Code") have system lock enabled. Even in unlocked table, these codes cannot be edited/deleted. "Lock" indicator shows next to code. Explicit unlock action required (National only) to modify.

Approval Required Workflow: Some tables are configured to require approval. When chapter edits a code, system sends Zoho email to National: "Chapter X requests modification to [table name]: [code] [change details]". National reviews, approves/denies in Zoho. Upon approval, change is applied to system. Chapter receives confirmation email.

Export/Backup: Staff can export lookup table as CSV for backup. Click "Export" button on table header. Download contains all codes and labels. Import feature available to bulk-load codes (admin only).

Browse Email Templates: Navigate to System Admin → Email Templates. Templates are grouped by module. Filter by module or search by template name (e.g., "Password Reset", "Invoice Due"). Each template shows Subject, From address, and preview of body.

Edit Email Template: Click template to open editor. Fields: Subject (required), Body (rich text or HTML), Reply-To address (optional), From address (defaults to chapter sender, override available), CC/BCC (optional, support dynamic variables). Dynamic variables available: {firstname}, {lastname}, {company}, {email}, {chapter}, etc. Insert via button picker or manual {{variable}} syntax. Save changes. All edits logged to audit trail.

Preview Email: Click "Preview" to see rendered template with sample data substituted. Shows how {firstname} and other variables will appear to recipient. Verify formatting, hyperlinks, signature.

Test Email: Click "Send Test" to email rendered template to current user's inbox. Useful for verifying formatting before deploying to production.

Non-Production Email Handling: In non-prod environment (Staging, QA), all emails have: (1) Subject prefix "[TEST] " added automatically, (2) Recipient swapped to system test email address (staff configures this per chapter in settings), (3) Warning banner in email body: "This is a test email. Do not respond." Prevents accidental customer contact during testing.

SMS Support: Select templates (password reset, appointment reminder, invoice due) support SMS delivery. Enable SMS toggle in template editor. SMS body is shorter, uses subset of variables. Select to deliver via Email, SMS, or Both.

Capability Control: Email template access requires L3 permission in Global Functionality module. Chapter staff with L2 can request National to modify templates.

Default Hierarchy: User preference → Chapter default → National default. System searches in that order. First non-null value wins. Example: If user sets "Default Date Format" to MM/DD/YYYY, that is used. If user hasn't set it, chapter's default is used. If chapter hasn't set it, National default is used.

14+ Configurable Settings:

• Date format (MM/DD/YYYY or DD/MM/YYYY)
• Currency symbol ($, €, £, ¥)
• Time zone (auto or override)
• Color scheme (light/dark/auto)
• Default event type (Conference, Webinar, etc.)
• Default invoice terms (Net 30, Net 60, etc.)
• Default payment method
• Notification preferences (email digest frequency)
• Dashboard layout (tiles or cards)
• Report visibility (standard/custom)
• And more...

Configure National Defaults: National staff (Super User) navigate to System Admin → Defaults. Tab: "National". Configure each setting. Save. These become the fallback for all chapters.

Configure Chapter Defaults: Chapter staff navigate to Settings → Defaults. Tab: "Chapter". Configure each setting that differs from National. Color indicator: orange = overridden from National, green = same as National. Chapter staff can also see "National Baseline" for reference.

Configure User Preferences: User navigates to My Settings → Preferences. Tab: "Personal". Configure personal overrides (e.g., "I prefer 24-hour time format"). All other settings cascade from chapter/national.

Reset to Parent: At any level (chapter or user), click "Reset to Parent" on a setting to clear override and inherit from parent level. Changes effective on next login.

Record Change History: On any record (contact, event, invoice, etc.), click "History" or "Audit Trail" button (usually top-right). Fly-out panel appears showing timeline of all changes. Each entry shows: timestamp, user who made change, field name, old value → new value. If user masqueraded, shows "[Masquerader] on behalf of [User]". Entries are immutable—cannot be edited or deleted.

Change History Filtering: Filter by date range, user, field name. Search for specific value. Export history as CSV.

System Event Logs: Navigate to System Admin → Event Logs. Log entries capture: API calls (with request/response), bulk imports (file name, row count), chapter modifications (who did what), system errors (stack trace). Filter by event type, date range, user, status (success/error). Useful for troubleshooting failed imports or identifying unauthorized changes.

Audit Reports: Navigate to System Admin → Audit Reports. Pre-built reports identify data discrepancies: (1) Accounts with no valid billing address, (2) Invoices with missing line items, (3) Contacts with duplicate email addresses, (4) Users with stale passwords (90+ days). Click report to view results as table. Table supports inline editing (edit-in-place) for bulk remediation. Save bulk changes, system logs remediation action to event log.

Permission for Audits: Change history visible to any user who can view a record. System event logs and audit reports require L3 (Admin) permission in Global Functionality. National staff can see global event logs; chapter staff see only their own chapter's events.

CRUD Operations: Create user with valid inputs (name, email). Verify password reset email is sent. Clone user, verify permissions copied. Edit user name/email/status. Verify changes persisted. Delete user with no history, verify removed from system.

Validation: Attempt create without Last Name—expect validation error. Attempt create with invalid email format—expect error. Duplicate email—expect error. Password reset with non-existent user—expect graceful failure.

Session & Authentication: Create new user, log in with temporary password, forced password reset flow. Verify new password meets policy (10 char, 3 of 4 types). Login with invalid password—expect locked after 3 attempts. Password reset via "Forgot Password"—verify email sent and reset link works.

Masquerade: Log in as L3 user, click "Login As" on another user. Verify vivid banner shows on new tab. Perform action (e.g., edit record), verify audit log attributes action to masquerader. Exit masquerade, verify return to original account.

Status Changes: Inactivate active user, verify login fails. Reactivate, verify login succeeds. Test confirmation prompts on status changes.

Permission Matrix (15 modules × 4 levels): For each module, create test users at L0, L1, L2, L3. Verify: (1) L0 user—module not in navigation, direct URL access returns 403; (2) L1 user—module visible, can view/search, Create/Edit/Delete buttons hidden; (3) L2 user—can create new records, edit own records, delete own records if no history; (4) L3 user—full access, all buttons visible, can edit any record, access admin screens.

Super User Flag: Create user with Super User enabled. Verify all 15 modules show L3 automatically. Individual module settings are greyed out. Disable Super User flag, verify individual module settings now editable.

Navigation Visibility: Test that permission changes immediately affect next login. User logs in with L1 Events, permission changed to L0 while logged in. On next login, Events module should be hidden.

Cross-Module Permissions: Verify permission in one module doesn't grant access to other modules. User with L3 Events but L0 Contacts should not see Contacts navigation.

Boundary Conditions: L2 user tries to delete record with history—expect error. L1 user tries to create record—expect permission denied. L0 user tries to access module via direct URL—expect 403.

Edit-in-Place (Unlocked Table): Open unlocked lookup table. Click code row, edit label, press Enter. Verify save occurs immediately, no page reload. Verify change appears in dropdown menus across system. Add new code, verify saved and available in dropdowns.

National Lock: Lock entire table from National. Chapter staff should see "Locked" banner, edit button disabled. Chapter staff attempts edit—expect error "Table is locked by National".

System Lock (Individual Code): Lock critical code within table. Chapter staff sees lock indicator next to code, cannot edit. Attempt edit—expect error "This code is system-locked".

Approval Workflow: Configure table for approval workflow. Chapter staff edits code. Verify Zoho email sent to National. National approves via Zoho. Verify change applied to system, chapter receives confirmation email. National denies approval, verify change not applied, chapter receives denial notification.

Export/Import: Export lookup table as CSV. Modify CSV locally, import back. Verify bulk codes loaded. Malformed CSV—expect import error with line numbers.

Template Customization: Edit email template, change subject, body, reply-to, from address. Save. Send test email. Verify received email matches edited template.

Dynamic Variable Substitution: Edit template to include {firstname}, {company}, {chapter}. Send test email. Verify variables replaced with actual values for user/account.

Non-Prod Handling: In QA environment, send email. Verify: (1) Subject has "[TEST]" prefix, (2) Recipient is test address (not original), (3) Body contains warning banner "This is a test email".

SMS Support: For SMS-enabled template, toggle SMS delivery on. Send test. Verify SMS received with shortened body (no HTML, variables substituted). Verify email not sent (or both sent if "Both" option selected).

Permission Control: L2 user attempts to edit template—expect "Permission Denied". L3 user can edit templates.

Preview & Test: Open template, click Preview, verify sample data rendered correctly. Click "Send Test", verify email arrives quickly.

3-Tier Hierarchy Cascade: Set National date format to MM/DD/YYYY. Chapter staff doesn't override, user doesn't set preference. Verify user sees MM/DD/YYYY. Chapter staff sets Chapter default to DD/MM/YYYY. Verify user now sees DD/MM/YYYY. User sets personal preference to MM/DD/YYYY. Verify user sees MM/DD/YYYY (personal wins). User resets to parent, verify cascade back to Chapter DD/MM/YYYY.

Color Indicators: Configure National default, Chapter override National. In chapter settings, verify green indicator on National value, orange indicator on Chapter override. Change Chapter back to match National, verify both green.

Missing Levels: If chapter hasn't set default and user hasn't set preference, system uses National. If National hasn't set it either, system uses hardcoded fallback (verify value in documentation).

Defaults Applied Correctly: Set time zone default to Pacific. Verify system displays all timestamps in Pacific. Change user preference to Eastern. Verify user sees times in Eastern. Other users unaffected.

Reset Functionality: Set Chapter default to custom value. Click "Reset to Parent". Verify reset to National default. User preference reset similarly.

Record Change History: Create record with initial data. Edit multiple fields (name, email, status, etc.). Click History panel. Verify all changes appear with: timestamp, user, field name, old value → new value. Verify order is chronological. Masquerade as user and edit, verify audit shows "[Masquerader] on behalf of [User]".

Change History Filtering: History with 50+ changes. Filter by date range (e.g., last week). Verify only changes in date range shown. Filter by field name (e.g., "Email"). Verify only email changes shown. Search for specific value. Verify matches found.

History Export: Click "Export History" to CSV. Open CSV locally, verify all changes present, format readable.

System Event Log: Perform bulk import, API call, chapter modification. Navigate to System Admin → Event Logs. Verify events logged with: timestamp, event type, user, status (success/error), details. Filter by event type, date, user. Search for specific event.

Audit Reports: Run pre-built report (e.g., "Accounts with no valid address"). Verify results displayed. Click report result row to view full record. Click "Edit in Place" on result, modify value, save. Verify bulk edit recorded to event log as audit action.

Permission Navigation: Create user with permissions in Events (L2) and Contacts (L0). Verify navigation shows Events module, hides Contacts. Create user with Super User. Verify all 15 modules visible in navigation.

Defaults Apply System-Wide: Set system default time zone to Pacific. Create event, verify event times display in Pacific. Create contact, verify contact interaction timestamps in Pacific.

Lookup Tables Used in All Modules: Create custom lookup table "Chapter Type". Edit value in Global Functionality → Lookup Tables. Verify dropdown in Contacts module reflects change. Verify dropdown in Events module reflects change.

Email System Across Modules: Customize email template for Events module ("Event Reminder"). Verify email sent from Events module uses customized template. Create new module that sends email (if available), verify it uses Global email system with same templates/variables.

L0=Restricted (no access, module hidden), L1=View (search/filter/view only), L2=Edit (create/edit own), L3=Admin (full access). Super User flag sets all to L3. Verify enforcement on every action: button visibility, error messages, URL-direct access.

Last Name, First Name, Email all required. System generates temporary password and sends password reset email immediately. User receives email, clicks link, sets permanent password. Verify all three fields validated before save.

User can only be deleted if they have zero record history (no transactions, events created, etc.). If history exists, Delete button is disabled and user must be inactivated instead. QA: Create user, assign record, attempt delete—expect error. Inactivate instead.

Only Active users can log in. Inactive users receive error "Your account is inactive. Contact administrator." Confirmation required when toggling status. QA: Inactivate user, attempt login—expect error. Reactivate, attempt login—expect success.

Only L3 users and National staff can masquerade. Opens new tab with vivid "[You are logged in as: FirstName LastName]" banner. All actions logged to audit trail with masquerader attribution. QA: L1 user attempts masquerade—expect disabled button. L3 user attempts—expect success with banner.

Minimum 10 characters, requiring 3 of 4 types: lowercase, uppercase, numeric, special character. Applied on user creation, password reset, and self-service password change. QA: Test valid (MyPassword123!), invalid (password, Password123 [no special], Password! [no number]).

Click History button on record to see fly-out panel showing field-level changes: what, when, who. Immutable—cannot edit or delete entries. Masquerade shows "[Masquerader] on behalf of [User]". QA: Create record, edit 3 fields, view history—verify all 3 changes captured accurately.

Audit reports display results in table. Click row to view record. Click edit button on cell to enable inline editing (edit-in-place). Press Enter to save, Escape to cancel. System logs bulk edit actions to event log. QA: Run audit report, use edit-in-place to fix 5 rows, verify all saved and logged.

National manages master lookup tables. Chapters inherit National tables, can customize if not locked. When new code added to National table, chapters automatically inherit. QA: National adds code to lookup table, verify appears in chapter's dropdown. National locks table, chapter cannot edit.

National can lock entire table preventing chapter edits, or lock individual critical codes (system lock). Chapter sees lock indicator, cannot modify. Attempt edit returns error "Table/Code is locked by National". QA: Lock table from National, chapter attempts edit—expect error.

Table configured for approval: Chapter modifies code, system sends Zoho email to National for review. National approves/denies. Approved changes applied to system, chapter receives confirmation. Denied changes not applied. QA: Configure approval workflow, chapter edits, verify Zoho email sent and approval triggers system change.

Critical codes (e.g., "Default Code") have system lock even in unlocked table. Cannot be modified or deleted without explicit National unlock action. QA: Identify system-locked code, attempt edit—expect error. National unlocks, attempt edit—expect success.

National defines baseline template. Each chapter can customize subject, body, reply-to, from address (within chapter limits). Customizations override National baseline for that chapter only. QA: National customizes template, chapter overrides with different subject. Verify chapter sees customized version, other chapters see National version.

Email templates support {firstname}, {lastname}, {company}, {email}, {chapter}, etc. System substitutes actual value when email sent. Variables not found are left blank or show error. QA: Template has {firstname}. Send email. Verify firstname substituted correctly. Test undefined variable—verify graceful handling (blank or error message).

In QA/Staging, all emails automatically: (1) Add "[TEST]" subject prefix, (2) Swap recipient to configured test address, (3) Include warning banner in body. Prevents accidental customer contact during testing. QA: Send email in QA environment. Verify subject prefix, recipient swap, banner present.

Some templates (password reset, appointment reminder, invoice due) support SMS. Editor toggle enables SMS delivery. Body shortened for SMS (no HTML). Variables substituted. User can choose Email, SMS, or Both. QA: Enable SMS on template, send test. Verify SMS received with shortened body.

User preference → Chapter default → National default. System searches in that order, uses first non-null value. QA: National sets time zone to Pacific. Chapter overrides to Eastern. User overrides to Mountain. Verify user sees Mountain. Verify other users see Eastern. Reset user to parent, verify Eastern (chapter level).

In settings, color indicator shows whether default differs from parent. Orange = value overridden (different from parent), Green = value same as parent, Neutral = no value set (inherited). QA: Set chapter default matching National—expect green. Change chapter default—expect orange. Reset to parent—expect green.

Some defaults are National-only (time zone), others available at all three levels (colors, formats). Verify in documentation which defaults are configurable at each level. QA: Attempt to set National-only default at chapter level—expect disabled/readonly field.

Email template editor provides fields: Subject (required), Body (rich text), Reply-To (optional), From (optional, defaults to chapter sender), CC (optional, supports dynamic variables), BCC (optional, supports dynamic variables). All fields validated for length. QA: Test very long subject—verify truncation or validation. Test special characters in From address—verify validation.

Setup: National creates new chapter in system. Chapter staff hired and assigned L2/L3 permissions for key modules.

Expected Behavior: (1) Chapter automatically inherits National lookup tables, (2) Chapter inherits National default values, (3) Chapter receives all email templates from National, (4) Chapter staff creates first users, assigns permissions, (5) Chapter staff customizes lookup tables (if not locked), overrides defaults (if available), customizes email templates (if L3).

Test Focus: Verify inheritance of lookup tables, defaults, and email templates. Test customization boundaries (what chapter can and cannot customize). Verify new users can be created with correct permissions.

Setup: Senior staff member with L3 permissions in Events, Contacts, and custom defaults departing. New hire replaces them.

Expected Behavior: (1) Click "Clone" on departing staff member's account. (2) System creates new user with copied permissions and defaults. (3) Staff updates name/email to new hire. (4) Inactivate departing staff member (cannot delete due to history). (5) New hire logs in with inherited permissions, no re-configuration needed.

Test Focus: Verify clone copies all permissions correctly (all 15 modules × their levels). Verify defaults cloned (personal overrides copied). Verify new user inherits all settings. Verify old user inactivation prevents login.

Setup: Chapter manager reviews user permissions to identify over-provisioned accounts (users with L3 who should only have L2).

Expected Behavior: (1) Navigate to System Admin → Users. (2) Click "View Permissions" modal to see all 15 modules × levels for each user. (3) Identify users with unnecessary L3 permissions. (4) Edit permission, downgrade from L3 to L2. (5) Save. (6) User receives no notification, but next login sees navigation updated and restricted actions disabled.

Test Focus: Verify permissions modal displays all 15 modules clearly. Verify downgrade takes effect on next login (not immediately). Test that downgrade doesn't grant accidental access to other modules.

Setup: Chapter needs to customize "Event Type" lookup table to add new code "Virtual Hybrid" not present in National baseline.

Expected Behavior: (1) If table is unlocked, click in lookup table, edit-in-place, add new code. Save immediately. (2) If table is locked, chapter sees lock banner, attempts edit, receives error. (3) Chapter contacts National via Zoho (if approval workflow enabled). (4) National reviews, approves. (5) Change applied. (6) New code immediately available in Event Type dropdown system-wide.

Test Focus: Test both locked and unlocked table scenarios. Test edit-in-place saves immediately without page reload. If approval workflow, verify Zoho email sent and approval triggers system change. Verify new code appears in dropdowns.

Setup: Chapter staff wants to customize "Dues Invoice Email" template: update subject line, add chapter logo, personalize with {firstname}.

Expected Behavior: (1) Navigate to System Admin → Email Templates. Filter to "Dues Invoice Email". (2) Click to edit. (3) Update Subject: "Invoice for {firstname}" (was generic). (4) Update Body: add chapter logo HTML, verify formatting. (5) Click Preview: verify sample data substituted, formatting correct. (6) Click "Send Test": receive test email with "[TEST]" subject prefix and warning banner. (7) Verify formatting, spelling, variables. (8) Save template. (9) Next actual invoice sent uses new template.

Test Focus: Verify edit, preview, and test send workflows. Test variable substitution with various data. Test non-prod email handling (prefix, recipient swap, banner). Verify saved template used for subsequent emails.

Setup: National sets default date format to MM/DD/YYYY. Chapter customizes to DD/MM/YYYY. User sets personal preference to MM/DD/YYYY. Three staff members with different override combinations.

Expected Behavior: (1) User with personal override sees MM/DD/YYYY. (2) User without personal override, from chapter with override, sees DD/MM/YYYY. (3) User without personal override, from chapter without override, sees MM/DD/YYYY (National). (4) Chapter changes override—all users in chapter see new format (unless they have personal override). (5) User resets personal preference—sees Chapter default. (6) National changes baseline—all chapters/users without overrides see new value.

Test Focus: Test cascade order exhaustively with multiple users and settings. Verify changes at one level don't affect other levels. Verify reset functionality works correctly. Test date formatting actually changes throughout system (reports, event display, etc.).

Setup: System admin suspects unauthorized changes to key records. Needs to review who changed what and when.

Expected Behavior: (1) Navigate to affected record, click History panel. (2) See all field changes, timestamps, users, old values → new values. (3) If masquerade detected, see "[Masquerader] on behalf of [User]" attribution. (4) Filter history by date range, user, field name. (5) Export history to CSV for documentation. (6) If incident appears to be API-based, navigate to System Admin → Event Logs. (7) Filter by event type (API), date range, user. (8) Identify suspicious API calls with timestamps and details. (9) Report findings to security team.

Test Focus: Verify history panel captures all changes accurately. Test filtering and export. Test system event logs capture API calls with enough detail for investigation. Verify masquerade attribution appears. Test audit trail immutability (cannot edit/delete history).

• Create user with valid inputs, verify password reset email sent
• Create user without Last Name, verify validation error
• Create user with duplicate email, verify error
• Clone user, verify all permissions copied
• Edit user name/email/status, verify changes persisted
• Inactivate user, attempt login, verify denied
• Reactivate user, attempt login, verify success
• Delete user with no history, verify removed
• Delete user with history, verify button disabled
• Masquerade as user, verify banner, verify action logged
• Exit masquerade, verify return to original account
• Login with invalid password 3x, verify account locked
• Password reset flow: click link, set password, verify policy enforced
• Self-service password reset: verify email link works

• L0 user: module not visible in nav, direct URL returns 403
• L1 user: module visible, Create/Edit/Delete buttons hidden, can view
• L2 user: can create own records, edit own, delete own (if no history)
• L3 user: full access, all buttons visible, access admin screens
• Super User flag enabled, verify all 15 modules show L3
• Super User flag disabled, individual module settings editable
• Change permission L1→L2, verify Create button appears on next login
• L2 user attempts to edit other user's record, verify error
• L1 user attempts to delete, verify button disabled or error
• Permission changes effective on next login (not immediately)
• L0 user does not see module in navigation

• Click code row, edit label, press Enter, verify saves immediately
• No page reload on edit-in-place save
• Add new code via edit-in-place, verify saved
• Delete code (if not system-locked), verify removed
• Deleted code no longer appears in dropdowns system-wide
• Locked table: edit button disabled, attempt edit returns error
• System-locked code: lock indicator shows, cannot edit
• New code from National table appears in chapter's dropdown
• Export table to CSV, verify format readable
• Import CSV, verify bulk codes loaded
• Malformed CSV import, verify error with line numbers

• Edit email template, change subject, body, save
• Send test email, verify received with edits
• Preview email, verify sample data rendered correctly
• Dynamic variable {firstname} substituted in preview and test
• Non-prod email: "[TEST]" prefix added, recipient swapped, banner present
• SMS-enabled template: SMS body shortened, no HTML
• Send via Email only, verify SMS not sent
• Send via SMS only, verify email not sent
• Send via Both, verify both email and SMS received
• L2 user attempts to edit template, verify permission denied
• L3 user can edit template
• Chapter customization: chapter edit overrides National baseline

• National sets date format MM/DD/YYYY, verify all users see it (no override)
• Chapter overrides to DD/MM/YYYY, verify users in chapter see DD/MM/YYYY
• User sets personal preference MM/DD/YYYY, verify overrides chapter
• User resets preference, cascade back to chapter DD/MM/YYYY
• National changes baseline, verify all users without override see new value
• Color indicators: green=same as parent, orange=override
• Reset to Parent button clears override
• User-only defaults cascade from chapter/national correctly
• Chapter-only defaults don't affect other chapters
• National-only defaults cannot be set at chapter/user level (readonly)
• Defaults actually applied: date format changes in reports, timestamps in correct timezone

• Create record, edit 3 fields, view history, verify all 3 changes captured
• History shows: timestamp, user, field name, old value → new value
• Masquerade: history shows "[Masquerader] on behalf of [User]"
• Filter history by date range, verify filtered correctly
• Filter history by user, verify shows only that user's changes
• Filter history by field name, verify shows only that field's changes
• Export history to CSV, verify format readable and complete
• History is immutable: cannot edit or delete entries
• System event log captures API calls, imports, errors
• Event log filterable by event type, date, user, status
• Audit reports: identify discrepancies and display in table
• Audit report: edit-in-place for bulk remediation, changes logged

Create Test Users: For each permission level (L0, L1, L2, L3), create at least one test user in each major module (Events, Contacts, Membership & Dues, etc.). Example:

• test.events.l0@example.com — Events L0, all others L0
• test.events.l1@example.com — Events L1, all others L0
• test.events.l2@example.com — Events L2, all others L0
• test.events.l3@example.com — Events L3, all others L0
• test.super.user@example.com — Super User flag enabled
• test.national.staff@example.com — Super User, represents National

This creates 4+ users per module × 15 modules = 60+ test accounts for comprehensive permission matrix testing.

Create Test Lookup Tables:

• Unlocked Table (Chapter Can Edit) — E.g., "Membership Level": Premium, Standard, Basic. Chapter staff can add/edit/delete codes.
• Locked Table (National Lock) — E.g., "Region": North, South, East, West. National has locked entire table. Chapter sees lock banner, cannot edit.
• Mixed Locking — E.g., "Status": Active (system-locked), Inactive (editable), Suspended (system-locked). Chapter can only edit Inactive.
• Approval Workflow — E.g., "Event Type": Conference (locked), Webinar (requires approval). Chapter attempts to modify Webinar, triggers Zoho approval workflow.

This mix of states allows testing locked/unlocked/approval scenarios.

Standard Email Templates: System pre-configured with 20+ templates per module:

• Password Reset — {firstname}, {email}, {reset_link}. SMS-enabled.
• Account Created — Welcome email with {firstname}, {company}, login instructions. Not SMS-enabled.
• Invoice Due — {firstname}, {invoice_amount}, {due_date}, {payment_link}. SMS-enabled.
• Event Reminder — {firstname}, {event_name}, {event_date}, {event_link}. SMS-enabled.
• And more...

Test Setup: Configure chapter to customize 2-3 templates (change subject, add chapter name, update reply-to). Configure SMS on 2 templates. Test non-prod email handling (recipient swap, [TEST] prefix, warning banner) on all templates.

National Defaults (Master):

• Date Format: MM/DD/YYYY
• Time Zone: UTC
• Currency: USD ($)
• Color Scheme: Dark
• Default Event Type: Conference
• Invoice Terms: Net 30

Chapter Overrides: Create test chapter with following overrides to National:

• Date Format: DD/MM/YYYY (override)
• Time Zone: US/Pacific (override)
• Currency: USD (same as National, no override)
• Color Scheme: Light (override)
• Invoice Terms: Net 60 (override)

User Preferences: Create test user with following personal overrides:

• Date Format: MM/DD/YYYY (same as chapter override, no personal override)
• Time Zone: US/Eastern (override chapter Pacific)
• Color Scheme: Auto (override chapter Light)

This setup allows testing the full cascade order: User→Chapter→National.

Create Test Records with History:

• Contact Record — Create contact (John Doe), edit name to John Smith, edit email 2x, inactivate. Total 5 changes in history.
• Event Record — Create event, edit description, change event type, update date 2x. Total 5 changes.
• Invoice Record — Create invoice, update amount, change status to Sent, change status to Paid, update notes. Total 5 changes.

Masquerade Records: Log in as L3 user, masquerade as L2 user, edit a record. Verify history shows "[Masquerader] on behalf of [L2 User]".

This setup allows testing: history filtering, history export, masquerade attribution, change accuracy.

Non-Production Email Settings: Configure QA/Staging environment:

• Email Recipient Swap: swap all outgoing emails to qa-inbox@example.com (single test mailbox)
• Email Subject Prefix: "[TEST]" automatically prepended
• Email Body Warning: "This is a test email. Do not respond." banner added automatically
• SMS Recipient Swap: (if SMS enabled) swap all SMS to test number +1-555-0100

API Test User: Create read-only API key for automated tests (if API testing in scope). Configure with L1 permissions (view only). Separate API key for bulk import testing with L3 permissions.

Performance Baseline: Document response times for key operations (user creation, permission change, lookup table edit, email send) in QA environment. Use as regression baseline after changes.